-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dandi-cli readme edit #1170
dandi-cli readme edit #1170
Conversation
Codecov ReportBase: 88.27% // Head: 88.90% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #1170 +/- ##
==========================================
+ Coverage 88.27% 88.90% +0.63%
==========================================
Files 73 76 +3
Lines 8817 9393 +576
==========================================
+ Hits 7783 8351 +568
- Misses 1034 1042 +8
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Co-authored-by: John T. Wodder II <jwodder@users.noreply.github.com>
Thank you @melster1010 !! While you are on the run across all the README's and have a good grip over the purpose etc of components -- would you might taking over dandi/handbook#66 to redo or finish up to bring it over the finish line one way or another (might no longer beneeded)? |
You're welcome @yarikoptic! Roni and I plan to discuss the next phase of my work on the DANDI docs, so I can add that to my backlog for Q1 2023 if that works for you. |
sure, unless we finalize it before then. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good as-is, but I've offered a couple of ideas for improvement along with one suggested change.
If the suggested change will cause confusion, let's move on without it. As for the ideas, we can discuss them here and/or accept their implicit suggestions (mainly of striking much of the content) in this PR.
-l, --log-level [DEBUG|INFO|WARNING|ERROR|CRITICAL] | ||
Log level name [default: INFO] | ||
-l, --log-level [DEBUG|INFO|WARNING|ERROR|CRITICAL] | ||
Log level (case insensitive). May be | ||
specified as an integer. [default: INFO] | ||
--pdb Fall into pdb if errors out | ||
--help Show this message and exit. | ||
|
||
Commands: | ||
download Download a file or entire folder from DANDI | ||
ls List .nwb files and dandisets metadata. | ||
organize (Re)organize files according to the metadata. | ||
register Register a new dandiset in the DANDI archive | ||
upload Upload dandiset (files) to DANDI archive. | ||
validate Validate files for NWB (and DANDI) compliance. | ||
delete Delete dandisets and assets from the server. | ||
digest Calculate file digests | ||
download Download a file or entire folder from DANDI. | ||
instances List known Dandi Archive instances that the CLI can... | ||
ls List .nwb files and dandisets metadata. | ||
move Move or rename assets in a local Dandiset and/or on... | ||
organize (Re)organize files according to the metadata. | ||
service-scripts Various utility operations | ||
shell-completion Emit shell script for enabling command completion. | ||
upload Upload Dandiset files to DANDI Archive. | ||
validate Validate files for NWB and DANDI compliance. | ||
validate-bids Validate BIDS paths. | ||
``` | ||
|
||
Each of the commands has a set of options to alter their behavior. Please run | ||
`dandi COMMAND --help` to get more information, e.g. | ||
Each of the commands has a set of options to alter its behavior. Run | ||
`dandi COMMAND --help` to get more information: | ||
|
||
``` | ||
$> dandi ls --help | ||
Usage: dandi ls [OPTIONS] [PATHS]... | ||
|
||
List .nwb files metadata | ||
Usage: dandi ls [OPTIONS] PATH|URL | ||
|
||
List .nwb files and dandisets metadata. | ||
|
||
The arguments may be either resource identifiers or paths to local | ||
files/directories. | ||
|
||
Accepted resource identifier patterns: | ||
- DANDI:<dandiset id>[/<version>] | ||
- https://dandiarchive.org/... | ||
- https://identifiers.org/DANDI:<dandiset id>[/<version id>] (<version id> cannot be 'draft') | ||
- https://<server>[/api]/[#/]dandiset/<dandiset id>[/<version>][/files[?location=<path>]] | ||
- https://*dandiarchive-org.netflify.app/... | ||
- https://<server>[/api]/dandisets/<dandiset id>[/versions[/<version>]] | ||
- https://<server>[/api]/assets/<asset id>[/download] | ||
- https://<server>[/api]/dandisets/<dandiset id>/versions/<version>/assets/<asset id>[/download] | ||
- https://<server>[/api]/dandisets/<dandiset id>/versions/<version>/assets/?path=<path> | ||
- dandi://<instance name>/<dandiset id>[@<version>][/<path>] | ||
- https://<server>/... | ||
|
||
Options: | ||
-F, --fields TEXT Comma-separated list of fields to display. | ||
An empty value to trigger a list of | ||
available fields to be printed out | ||
-f, --format [auto|pyout|json|json_pp|yaml] | ||
-f, --format [auto|pyout|json|json_pp|json_lines|yaml] | ||
Choose the format/frontend for output. If | ||
'auto', 'pyout' will be used in case of | ||
multiple files, and 'yaml' for a single | ||
file. | ||
-r, --recursive Recurse into content of | ||
dandisets/directories. Only .nwb files will | ||
be considered. | ||
-J, --jobs INTEGER Number of parallel download jobs. [default: | ||
6] | ||
--metadata [api|all|assets] | ||
--schema VERSION Convert metadata to new schema version | ||
--help Show this message and exit. | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It may be out of scope for this PR, but this section seems like it can be simplified to letting the user know that they can run dandi --help
and dandi <subcommand> --help
to get manpages. Listing sample output means we'll need to keep updating this section every time the CLI changes its interface.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That had crossed my mind too, wasn't sure how often this changed. Added to my Phase 2 docs backlog for 2023.
## Development/contributing | ||
## Third-party Components | ||
|
||
Please see [DEVELOPMENT.md](./DEVELOPMENT.md) file. | ||
**dandi/tests/skip.py** -- from https://github.com/ReproNim/reproman, as of v0.2.1-40-gf4f026d | ||
Copyright (c) 2016-2020 ReproMan Team |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also out of scope for this PR, but I think this section can be struck. I don't think it adds any useful information about DANDI CLI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added to my Phase 2 docs backlog for 2023.
|
||
### dandi/tests/skip.py | ||
* To learn how to interact with the DANDI archive and for examples on how to use the DANDI Client in various use cases, | ||
see [the handbook](https://www.dandiarchive.org/handbook/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it might be useful to highlight sections of the handbook specifically related to the CLI:
see [the handbook](https://www.dandiarchive.org/handbook/). | |
see [the handbook](https://www.dandiarchive.org/handbook/), | |
specifically the sections on using the CLI to | |
[download](https://www.dandiarchive.org/handbook/12_download/) and | |
[upload](https://www.dandiarchive.org/handbook/13_upload/) `Dandisets`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that specific guidance would be useful. Added to my Phase 2 docs backlog for 2023.
There are 2 approvals, and documentation can always be improved more, so I will just proceed as is for now. Thanks everyone!!! |
Edit readme for stylesheet compliance/grammar/clarity/consistency.